Method for NPA split processing

ABSTRACT

A system and method for numbering plan area (NPA) split processing is disclosed. In one implementation, a query is received during a permissive dialing period. The query comprises a destination location that is associated with a first NPA. It is determined whether a first call processing record identifies a service that is NPA sensitive. The first call processing record is associated with a destination location that is undergoing a NPA split. The first call processing record is identified by the destination location and the destination location is associated with a first NPA. A second call processing record is then used for processing in place of the first call processing record when the first call processing record identifies a service that is NPA sensitive. The second call processing record is associated with the destination location that is undergoing an NPA split. The second call processing record is identified by the destination location and the destination location is associated with a second NPA.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 11/542,299, filed Oct. 2, 2006 now U.S. Pat. No. 7,372,954,which is a continuation of U.S. patent application Ser. No. 10/054,764(now U.S. Pat. No. 7,139,385), filed Jan. 18, 2002, the entirety of eachof which is hereby incorporated by reference.

TECHNICAL FIELD

The present invention relates to telecommunication systems and inparticular to a method for NPA split processing on a service controlpoint.

BACKGROUND

During an NPA split, one or more new NPAs are created and assigned to anarea formerly having only a single assigned NPA. The process ofassigning new NPAs to all of the affected telephone lines occurs over aperiod of time. During this time, which is referred to as the permissivedialing period, calls can be placed to a telephone line using either theold or new NPA. In some networks, call processing records are duplicatedduring the permissive dialing period. The original call processingrecord is identified by the telephone number with the old NPA, and theduplicate call processing record is identified by the telephone numberwith the new NPA. Problems can arise when changes are made to one callprocessing record but not the other during the permissive dialingperiod.

Several approaches have been discussed to solve this problem. Oneapproach is described in U.S. Pat. No. 5,978,462. With the approachdescribed in the '462 patent, all call processing records identified bytelephone numbers with old NPAs are modified to include a pointer tocall processing records identified by telephone numbers with new NPAs.Another approach is described in U.S. Pat. No. 6,289,095. Under thisapproach, pertinent parameters of all incoming query messages arechanged in the network signaling interface of the SCP to replace the oldNPA with the new NPA before the message is sent to the application levelsoftware of the SCP. This approach can result in undue extra processingtime as not all messages may need to have the old NPA replaced with thenew NPA.

There is a need, therefore, for a new method for NPA split processing ona service control point.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a telecommunication network of a preferredembodiment.

FIG. 2 is an illustration of a service control point of a preferredembodiment.

FIG. 3 is an illustration of an NPA split table of a preferredembodiment.

FIG. 4 is an illustration of a service control point of anotherpreferred embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

By way of introduction, these preferred embodiments can be used toovercome problems encountered during a permissive dialing period of anNPA split. These preferred embodiments also yield several advantagesover prior art approaches to this problem. Specifically, these preferredembodiments do not require changes to be made to an existing callprocessing record to include a pointer to a new call processing recordidentified by a telephone number with a new NPA. Additionally, unlikeprior approaches that require changes to be made to all incoming querymessages to a service control point, these preferred embodiments do notrequire extra processing for services that are not NPA sensitive.

System Overview

Turning now to the drawings, FIG. 1 is a block diagram of atelecommunication network 100 of a preferred embodiment. In thispreferred embodiment, the telecommunication network 100 is part of apublic-switched telephone network (PSTN) and is implemented as anadvanced intelligent network (AIN) using the Signaling System 7 (SS7)network. The network 100 comprises a plurality of service switchingpoints (SSP A 110, SSP B 120, SSP C 130), a local signal transfer point(STP) 140, a regional STP 150, a service control point (SCP) 160, aservice management system (SMS) 170, and an intelligent peripheral (IP)180. In FIG. 1, the dashed lines represent SS7 links, the solid linesbetween the SSPs 110, 120, 130 represent inter-office trunking, and thesolid lines between the SSPs 110, 120, 130 and the telephone stations(such as telephone 190) and the intelligent peripheral 180 representtelephone lines. Although any suitable component can be used, in onepreferred embodiment, the SCP 160 is a Telcordia ISCP™, and theintelligent peripheral 180 is IBM's Resource Manager. Another brand ofintelligent peripheral that provides similar functionality to IBM'sResource Manager is Lucent's Compact Service Node. In this preferredembodiment, the intelligent peripheral 180 has a direct data networkconnection to the SCP 160; however, this type of connection is notrequired.

The SSPs 110, 120, 130 are SS7/AIN-enabled central offices with physicalswitching devices that route calls from one telephone station to anotherat the same or different SSP. The local STP 140 transfers signalingmessages used during call set-up and routing between the SSPs 110, 120,130, and the regional STP 150 transfers signaling messages between theSCP 160 and the local STP 140. The SCP 160 provides execution ofspecialized services for subscribing customers and can communicate withexternal databases. An SCP with an integrated service creationenvironment is referred to as an integrated SCP (ISCP). For simplicity,the term SCP shall be used herein to refer to either an SCP or an ISCP.The intelligent peripheral 180 can be used by a calling party to accessand change call processing records stored on the SCP 160. In onepreferred embodiment, the intelligent peripheral 180 comprises a profilemanagement system having an interactive voice response (IVR) system thatrecognizes information entered via the calling party's keypad or thatutilizes voice recognition, a web-based customer change tool, or anyother similar automated system used for customer-initiated change.

In this network 100, telephone lines are assigned a ten-digit telephonenumber (TN). The first three digits of the TN are referred to as thenumbering plan area (NPA) number, or area code. The next three digitsare referred to as the NXX, which identifies an SSP that handles callswithin a geographic area. The last four digits are referred to as theXXXX, which uniquely represents a particular telephone line in an SSP.The SCP 160 contains call processing records (CPRs) that are identifiedby TNs, and CPRs identify database services associated with varioustelephone lines. Often, a person paying a telephone company for use ofthe telephone line pays an addition fee for the database services. Forsimplicity, a person associated with a given telephone line will bereferred to herein as a “subscriber” regardless of whether that personpays an additional fee for the database services or whether the servicesare provided free of charge. In operation, a query containing a TN issent from an SSP to the SCP 160. Application level software in the SCP160 stores the TN as a call variable, which is used to locate andexecute the CPR identified by the TN. This CPR is often referred to as a“trigger CPR” because it is the first CPR that is executed by theapplication level software on the SCP 160. The CPR describes theservices subscribed to by the subscriber and instructs the SCP 160 toperform some service. The results of the service are then sent back tothe SSP.

When a local exchange carrier (LEC) runs out of ten-digit telephonenumbers within a particular area, the LEC creates a new NPA and assignsthe new NPA to some of the existing telephone numbers in that area. Theprocess of creating and assigning one or more new NPAs to an areaformerly having only a single assigned NPA is referred to as an NPAsplit. The process of assigning the NPAs to all of the affected linesoccurs over a period of time, and it is often unclear when a particulartelephone line has been assigned a new NPA. To assist in the transition,the LEC can provision a period of time during which calls can be placedto the telephone line using either the old or new NPA. Even though callscan be placed to the telephone line with either NPA, the telephone linewill, in fact, only have a single TN—either one with the old NPA or onewith the new NPA. Accordingly, when a query is sent to the SCP 160during the permissive dialing period, the query will contain whatever TNis assigned to the telephone line at that time, regardless of whether acaller dialed the TN with the old or new NPA.

During the permissive dialing period, existing trigger CPRs for TNsaffected by the NPA split are duplicated by service assurance andprovisioning personnel. The duplicate trigger CPR (the “new CPR”)contains the same information as the original trigger CPR (the “oldCPR”) but is identified by the TN with the new NPA (unlike the old CPR,which is identified by the TN with the old NPA). Both the new and oldCPRs exist on the SCP 160 during the permissive dialing period. Beforethe SSP converts to the new NPA, the TN will have the old NPA, and,accordingly, the old CPR will be used. After the SSP converts to the newNPA, the TN will have the new NPA, and the new CPR will be used. At theend of the permissive dialing period, the old CPR will be deleted sothat only the new CPR exists.

Problems can be encountered during the permissive dialing period withservices that are NPA sensitive. As used herein, a service is NPAsensitive if the operation or effect of the service depends on whetherthe telephone line is identified by the old or new NPA. A service is NPAsensitive, for example, if a change made to either but not both of theold and new CPRs during the permissive dialing period will result inimproper service execution. A service is also NPA sensitive if theservice checks a storage location storing one but not both of thefollowing, a telephone number with an old NPA and a telephone numberwith a new NPA. Examples of specific services that are NPA sensitiveinclude the following services by the assignee of the present invention:Outgoing Call Control (OCC), which blocks certain calls from being madefrom the subscriber telephone line; Privacy Manager, which requirescallers to identify themselves in order to complete a call if thetelephone number of the caller cannot be identified by Caller ID; andPositive ID, which allows calls to be placed to a subscriber only if thecaller's telephone number is on an accept list. The OCC service will beused below for illustration purposes. It should be noted that thefollowing embodiments can be applied to other NPA sensitive services andshould not be limited to the services mentioned above.

Two situations in which problems can occur are in-call processing andprofile management. Problems can also occur in other situations, such aswhen a service checks a storage location to determine what telephonenumber is stored therein. Those situations will now be discussed.

In-Call Processing

During in-call processing, a query is sent from the SSP to the SCP 160in response to a trigger (e.g., an originating or terminating trigger)to determine what services should be applied to the call. The querycontains the TN of the triggering telephone line, and the SCP 160 usesthe TN to locate and execute the CPR identified by the TN. As describedabove, during the permissive dialing period, two CPRs exists for thesubscriber. If changes were made to one of those CPRs but not the otherduring the permissive dialing period, the CPR retrieved by the SCP 160might be erroneous or out of date. Consider the situation in which aservice allows a subscriber to make a change to one but not both of theCPRs during the permissive dialing period; for example, when thesubscriber changes the duplicate CPR to turn on an Outgoing Call Control(OCC) service. If the subscriber's SSP has not yet converted to the newNPA, the SSP will send the SCP 160 a query with the TN having the oldNPA, and the SCP 160 will retrieve the old CPR, which indicates that theOCC service is off. Because the change was made to a different CPR thanthe one retrieved in response to the query, the SCP 160 did not providethe appropriate service.

To overcome this problem, the SCP 160 can analyze the servicesidentified in the CPR to determine if they are NPA sensitive. As shownabove, one example of a service that is NPA sensitive is one that allowsa change to be made in either but not both of the old and new CPRsduring the permissive dialing period. In this preferred embodiment, if aservice is NPA sensitive, changes made during the permissive dialingperiod are forced to be made to the new CPR regardless of whether the TNhas the old or new NPA. Further, the duplicate CPR is used duringin-call processing regardless of whether the trigger contains the TNwith the old or new NPA. In other words, to guarantee that the mostcurrent subscriber data is used by the SCP 160, this preferredembodiment uses the new CPR regardless of the NPA that was sent from theSSP.

FIG. 2 is an illustration of a service control point 200 that willfurther illustrate this preferred embodiment. The SCP 200 comprisessystem level software 205 and application level software 210. Theapplication level software 210 includes a feature interactive manager(FIM) 215 and an NPA split utility 220. The operation of thesecomponents will be illustrated in conjunction with an example in whichan SSP 225 sends a query with a TN of 512-372-5414 to the SCP 200 duringa permissive dialing period before the NPA is changed to 479. Thenetwork element of the SCP 200 receives a transaction request via thesignaling network at the network interface (act 230). The messagecontains the User ID 512-372-5414. The system level software 205forwards the message to the subscriber's call processing record in theSCP 200 with the name 512-372-5414 (act 235).

The application level software 210 stores the TN identified in the queryin a call variable and accesses the CPR identified by this TN(512-372-5414). The names of the subscribed services and data specificto 512-372-5414 are loaded into memory, and control is passed to the FIM215 (act 240). The FIM 245 determines whether any of the subscribedservices are eligible for an NPA check (i.e., whether any of thesubscribed services are NPA sensitive) (act 245). If the subscribedservices are not NPA sensitive, the FIM 215 analyzes the subscribedservices to determine their order of execution (act 250), executes theservices in the correct order (act 255), and sends the response to thenetwork interface of the SCP 200 (act 260).

If the subscribed services are NPA sensitive, control is passed to theNPA split utility 220, which determines whether the query was sent inthe permissive dialing period (act 265). To do this, the NPA splitutility 220 uses an NPA split table 300 (see FIG. 3). The NPA splittable 300 lists the NPA/NXX combinations that are currently inpermissive dialing and contains (at a minimum) the following columns:Old NPA, Old NXX, New NPA, Permissive Dialing Start Date, and PermissiveDialing End Date. Service assurance and provisioning personnel (i.e.,CNOC) can add rows to the table 300 before the beginning date forpermissive dialing and can remove the rows anytime after permissivedialing. In operation, the NPA split utility 220 searches the NPA splittable 300 using the NPA and NXX combination from the TN presented in thequery and determines whether the query was sent in the permissivedialing period. If the query was not sent in the permissive dialingperiod, acts 250-260 are performed using the data present in the oldCPR. If the query was sent in the permissive dialing period, global callvariables are changed to reflect the new NPA of 479 (act 270). The newCPR is then retrieved (act 275), and acts 250-260 are performed usingthe data present in the new CPR.

When the Telcordia ISCP™ is used and an entry is found in the NPA splittable, the relevant $Q call variables (those sent in the query from theSSP that contains the old NPA/NXX) will be changed to reflect the newNPA, and the new trigger CPR will be executed. The following table showssome of the trigger types that can utilize the NPA split utility 220 andthe associated call variables that can be changed to reflect the newNPA. Different graphs are used, depending on trigger type, due to thedifferent Q call variables that need to be reset, using the new NPA ofthe triggered number. The call variable $QSERVICEKEY identifies theservice key (i.e., the CPR name) to be used to process the call, and thecall variable $QUSERID contains the userid in the incoming querymessage. The value can be the dialed number, a trunk group number, or aprivate facility ID. The checking of the NPA split table and thereplacing of the various call variables can be done in the FIM 215. Itshould be noted that the following claims should not be limited to thetrigger types listed below and that many other existing and futuretrigger types can benefit from these preferred embodiments.

Call Variables Being Call Variables Names as Changed to They Appear inTrigger Type Reflect New NPA the Telcordia SCP Terminationatte Callednumber $QCALLEDPARTYID Dialed number $QDIALEDNUMBER Name of servicelogic $QSERVICEKEY to execite user ID in incoming query $QUSERID messageTN entered on keypad $QCOLLECTEDDIGITS by caller 10digit Called Number$QCALLEDPARTYID Dialed Number $QDIALEDNUMBER Name of service $QSERVIEKEYlogic to execute OffHookDelay Calling number $QCALLINGPARTYIDCDPAccessCode Billed Number $QCHARGENUMBER CDPInterComCode Name ofservice $QSERVICEKEY logic to execute PRIBChannel user ID in the$QUSERID incoming query message

Profile Management

With the profile management feature of this preferred embodiment, asubscriber can make changes to a subscribed service directly on the SCP(instead of going through an SMS for data update) by using an IVR systemlocated on the SCP or on an intelligent peripheral outside of the SCP orby using a web-based change tool. If the service is NPA sensitive,however, problems can arise if changes are made to the original CPRinstead of the duplicate CPR. In that situation, changes made during thepermissive dialing period by the subscriber will not be used after theSSP changes to the new NPA. Consider the situation in which a subscriberdials into the intelligent peripheral 180 from his telephone line duringthe permissive dialing period to turn on an Outgoing Call Control (OCC)service. If the subscriber's SSP has not yet converted to the new NPA,his SSP will send the SCP a message with the TN having the old NPA, and,accordingly, the SCP will update the subscriber's original CPR toindicate that the OCC service is on. When the subscriber makes a callfrom his telephone line after his SSP converts, his SSP will send aquery to the SCP with a TN having the new NPA. The SCP will retrieve theduplicate CPR, which reflects that the OCC service is in the off statesince the change made by the subscriber was only applied to the old CPR.Accordingly, the subscriber's calls are not screened even though heturned on the service using profile management. The subscriber willeither call his telephone company to report a problem (“call in atrouble ticket”) or access profile management again to turn on the OCCservice.

As another example, if a subscriber accesses profile management fromsomeone else's telephone line (i.e., a telephone line other than the onewith the AIN trigger), the subscriber will be asked by the IVR system ofthe intelligent peripheral to input his telephone number to identify theCPR that will be changed. Since the subscriber does not know when hisSSP will convert, he enters the TN with the old NPA using the IVRsystem. In this example, the subscriber changes a PIN that is used totemporarily override the blocking of the OCC service. Because thesubscriber entered the TN with the old NPA, the new PIN will be storedonly in the original CPR. Accordingly, after the subscriber's SSPconverts, the new PIN will not work because the duplicate CPR has theold PIN. Similarly, if the subscriber adds access codes during thepermissive dialing period to allow incoming calls not to be blocked,only the old CPR will be updated. After the SSP converts, callers cannotreach the subscriber using the new access codes because those codes werenot stored in the new CPR.

FIG. 4 is a block diagram of an SCP 400 that illustrates this preferredembodiment. The SCP 400 comprises system level software 405 andapplication level software 410. The application level software 410comprises a plurality of profile management CPRs 420, 425, 430 and anNPA split utility 435. Each of the profile management CPRs 420, 425, 430are associated with a respective service. The services of profilemanagement CPRs 420 and 425 are NPA sensitive, while the service ofprofile management CPR 430 is not. In this embodiment, each of theprofile management CPRs 420, 425, 430 is associated with a differentdial-in telephone number, and a subscriber selects which profilemanagement CPRs 420, 425, 430 he wishes to use by dialing theappropriate number. The subscriber is then connected to an intelligentperipheral that starts the IVR process (act 440). Assume that thesubscribers TN is 512-372-5414 and that the subscriber calls theintelligent peripheral during the permissive dialing period before theNPA is changed to 479.

After the IVR is started, the network element of the system levelsoftware 405 receives a transmission request via the signaling networkat the network interface of the SCP 400 (act 445). The message containsthe UserID of 512-372-5414. The system level software 405 then forwardsthe message to the service-specific profile management CPR in theapplication level software 420 (the AIN application) based on the numberdialed by the subscriber (act 450). If the profile management CPR is NPAsensitive (such as profile management CPRs 420 and 425), control ispassed to the NPA split utility 435. The NPA split utility 435 searchesthe NPA split table 300 using the NPA and NXX combination from the TNpresented in the query and determines whether the query was sent in thepermissive dialing period. If the query was not sent in the permissivedialing period, data present in the original CPR is loaded into memory,and control is passed to profile management CPR 425 (act 460). Thesubscriber then updates data in his old CPR. If the query was sent inthe permissive dialing period, global call variables are changed toreflect the new NPA of 479 (act 465). The subscriber's new CPR isretrieved and loaded into memory, and control is passed to profilemanagement CPR 420 (act 470). The subscriber then updates data in thenew CPR. In one preferred embodiment, the Telcordia ISCP™ is used. Callvariables sent in the AIN query from the switches to the Telcordia ISCP™are referred to as Q call variables. If global call variables arechanged to reflect the new NPA, the logic replaces the old NPA with thenew NPA in the $QANI call variable. The $QANI call variable is theten-digit line number as found in the initial profile management query.

If the profile management CPR is not NPA sensitive (profile managementCPR 430), the subscriber updates data without using the NPA splitutility 435. Services that are not NPA split sensitive can use eitherthe subscriber's original or duplicate CPRs during the permissivedialing period or can allow a subscriber to make a change to a CPR thatis not keyed to any NPA. For example, services that provide a localrouting service are not NPA split sensitive if they can use eitheroriginal or duplicate CPRs during the permissive dialing period, but donot allow changes to be made to the CPRs during the permissive dialingperiod. Accordingly, it does not matter which of the two CPRs theservice uses during the permissive dialing period. As another example,some abbreviated dialing services, such as 311, allow changes to be madeto a CPR during the permissive dialing period but do not use originaland duplicate CPRs during a permissive dialing period because these CPRsare not identified by a TN of a subscriber. As yet another example, theDisaster Routing Service offered by the assignee of the presentinvention has an IVR that allows customers to change PIN numbers androuting options. The subscriber data for this service is stored in CPRswhose names do not contain NPAs, and therefore, are not affected by NPAsplits.

Other Situations

As mentioned above, problems associated with NPA sensitive services canoccur in situations other than in-call processing and profilemanagement. For example, a problem can occur with a service that checksa storage location to determine what telephone number is stored therein.One such service is an Internet Caller ID (ICID) service provided by theassignee of the present invention. With ICID, a subscriber who is usinghis telephone line to use the Internet receives a pop-up window withCaller ID information when someone calls his line while he is on theInternet. In operation, an application on the subscriber's computerstores the TN of the subscriber's telephone line in a registrationserver. When an incoming call arrives at the subscriber's SSP, a triggeris sent to an SCP, which consults the registration server to see if thesubscriber's TN is stored therein. If it is, the SCP will enable theICID functionality. A problem occurs during an NPA split when thesubscriber's application stores the TN with old NPA, and the SCP checksthe registration server for the TN with the new NPA, or vice versa. Tosolve this problem, the SCP can check the registration server for bothTNs. In operation, the SCP assigns the TN with the old NPA to a callvariable and determines if that number is stored in the registrationserver. If it is not, the SCP replaces the old NPA with the new NPA inthe call variable and determines if the TN with the new NPA is stored inthe registration server.

Although the embodiments were described above with respect to an NPAsplit, these embodiments can be used with any kind of change to anumbering plan. For example, changes can be made to codes other thanarea codes, such as with telephone numbers in countries that usedifferent numbering plans. Further, although these preferred embodimentsused telephone numbers to uniquely identify a telephone line and asubscriber's CPR, any type of identifier can be used. It should also benoted that originating or terminating SSPs can be used to send a queryto an SCP. Additionally, while the telephone networks were describedabove as AIN networks, other types of networks can be used. Moregenerally, any suitable type of telecommunication element (e.g.,switches, processors) can be used to implement the methods describedabove. Further, computer-readable media having computer-readable codeembodied therein for implementing these methods can be used.

It is intended that the foregoing detailed description be understood asan illustration of selected forms that the invention can take and not asa definition of the invention. It is only the following claims,including all equivalents, that are intended to define the scope of thisinvention.

1. A method for numbering plan area (NPA) split processing, the methodcomprising: receiving a query comprising a destination locationassociated with a NPA; determining whether the NPA is undergoing a NPAsplit; determining whether a service associated with the NPA and thedestination location is NPA sensitive; and using a second callprocessing record in place of a first call processing record when it isdetermined that the NPA is undergoing a NPA split and the serviceassociated with the NPA is NPA sensitive.
 2. The method of claim 1,wherein the query is received during a permissive dialing period.
 3. Themethod of claim 1, further comprising: determining that the query wasreceived during a permissive dialing period.
 4. The method of claim 1,wherein the first call record identifies whether the service is NPAsensitive.
 5. The method of claim 1, further comprising: using the firstcall processing record when it is determined that the NPA is undergoinga NPA split and the service associated with the NPA is not NPAsensitive.
 6. The method of claim 1, wherein a service is NPA sensitiveif a change made to either, but not both of, the first and second callprocessing records will result in improper service execution.
 7. Acomputer-readable storage medium comprising a set of instructions fornumbering plan area (NPA) split processing, the set of instructions todirect a processor to perform acts of: receiving a query comprising adestination location associated with a NPA; determining whether the NPAis undergoing an NPA split; determining whether a service associatedwith the NPA and the destination location is NPA sensitive; and using asecond call processing record in place of a first call processing recordwhen it is determined that the NPA is undergoing a NPA split and theservice associated with the NPA is NPA sensitive.
 8. Thecomputer-readable storage medium of claim 7, further comprising a set ofinstructions to direct a processor to perform acts of: determining thatthe query was received during a permissive dialing period.
 9. A systemfor numbering plan area (NPA) split processing, the system comprising: anetwork element operative to: receive a query comprising a destinationlocation associated with a NPA; determine whether the NPA is undergoinga NPA split; determine whether a service associated with the NPA and thedestination location is NPA sensitive; and use a second call processingrecord in place of a first call processing record when it is determinedthat the NPA is undergoing an NPA split and the service associated withthe NPA is NPA sensitive.
 10. A method for numbering plan area (NPA)split processing, the method comprising: receiving a query comprising adestination location associated with a NPA undergoing a NPA split;retrieving a first call processing record associated with thedestination location and a service; determining whether the service isNPA sensitive; and changing a call variable associated with thedestination location when it is determined that the service is NPAsensitive.
 11. The method of claim 10, wherein the query is receivedduring a permissive call period.
 12. The method of claim 10, furthercomprising: determining that the query was received during a permissivecall period.
 13. The method of claim 10, wherein changing the callvariable comprises: changing a NPA in the call variable to a new NPA.14. The method of claim 10, further comprising: retrieving a second callprocessing record associated with the changed call variable; and usingthe second call processing record in place of the first call processingrecord.
 15. The method of claim 10, further comprising: identifying thenew NPA from a table correlating the NPA undergoing the NPA split withthe new NPA.
 16. A computer-readable storage medium comprising a set ofinstructions for numbering plan area (NPA) split processing, the set ofinstructions to direct a processor to perform acts of: receiving a querycomprising a destination location associated with a NPA undergoing a NPAsplit; retrieving a call processing record associated with thedestination location and a service; determining whether the service isNPA sensitive; and changing a call variable associated with thedestination location when it is determined that the service is NPAsensitive.
 17. The computer-readable storage medium of claim 16, furthercomprising a set of instructions to direct a processor to perform actsof: determining the query was receiving during a permissive call period.18. A system for numbering plan area (NPA) split processing, the systemcomprising: a network element operative to: receive a query comprising adestination location associated with a NPA undergoing a NPA split;retrieve a call processing record associated with the destinationlocation and a service, determining whether the service is NPAsensitive; and changing a call variable associated with the destinationlocation when it is determined that the service is NPA sensitive.